Skip to content

Conversation

@mipo256
Copy link

@mipo256 mipo256 commented Oct 21, 2025

No description provided.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Oct 21, 2025
You can write technology-specific extensions by using javadoc:org.springframework.boot.actuate.endpoint.web.annotation.EndpointWebExtension[format=annotation] and javadoc:org.springframework.boot.actuate.endpoint.jmx.annotation.EndpointJmxExtension[format=annotation].
These annotations let you provide technology-specific operations to augment an existing endpoint.

NOTE: As of now, it is possible to have only a single extension per an individual javadoc:org.springframework.boot.actuate.endpoint.annotation.Endpoint[format=annotation].
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR but I don't think this is accurate as an individual endpoint can have both a Web extension and a JMX extension. It's only multiple JMX extensions or multiple Web extensions that are not supported.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is correct, thank you for the clarification, @wilkinsona. Changed the wording here.

@mipo256 mipo256 requested a review from wilkinsona October 21, 2025 12:10
@wilkinsona wilkinsona added this to the 3.4.x milestone Oct 21, 2025
@wilkinsona wilkinsona added type: documentation A documentation update and removed status: waiting-for-triage An issue we've not yet triaged labels Oct 21, 2025
You can write technology-specific extensions by using javadoc:org.springframework.boot.actuate.endpoint.web.annotation.EndpointWebExtension[format=annotation] and javadoc:org.springframework.boot.actuate.endpoint.jmx.annotation.EndpointJmxExtension[format=annotation].
These annotations let you provide technology-specific operations to augment an existing endpoint.

NOTE: As of now, it is not possible to have multiple javadoc:org.springframework.boot.actuate.endpoint.web.annotation.EndpointWebExtension[format=annotation] or javadoc:org.springframework.boot.actuate.endpoint.jmx.annotation.EndpointJmxExtension[format=annotation] extensions per a single javadoc:org.springframework.boot.actuate.endpoint.annotation.Endpoint[format=annotation]. However, it is possible to have both javadoc:org.springframework.boot.actuate.endpoint.web.annotation.EndpointWebExtension[format=annotation] and javadoc:org.springframework.boot.actuate.endpoint.jmx.annotation.EndpointJmxExtension[format=annotation] for a single javadoc:org.springframework.boot.actuate.endpoint.annotation.Endpoint[format=annotation]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than this note, I wonder if it would be better to add a sentence to the proceeding paragraph. Something like the following:

"An endpoint may have at most one extension of each type".

WDYT?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense @wilkinsona, I applied the change

@wilkinsona wilkinsona self-requested a review October 21, 2025 14:54
@wilkinsona wilkinsona added the status: waiting-for-feedback We need additional information before we can continue label Oct 21, 2025
@snicoll snicoll changed the title Polishing: Clarified documentation about Endpoint Extensions Document that Actuator endpoint may have at most one extension of each type Oct 25, 2025
Signed-off-by: mipo256 <mikhailpolivakha@email.com>
Signed-off-by: Mikhail Polivakha <mikhailpolivakha@email.com>
@wilkinsona wilkinsona removed the status: waiting-for-feedback We need additional information before we can continue label Oct 29, 2025
@snicoll snicoll self-assigned this Oct 30, 2025
snicoll pushed a commit that referenced this pull request Oct 30, 2025
See gh-47740

Signed-off-by: mipo256 <mikhailpolivakha@email.com>
@snicoll snicoll closed this in 99f58de Oct 30, 2025
@snicoll snicoll modified the milestones: 3.4.x, 3.4.12 Oct 30, 2025
@snicoll
Copy link
Member

snicoll commented Oct 30, 2025

Thanks for following up @mipo256.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: documentation A documentation update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants